Some exemplary use cases

Here are some use cases for which this product is useful:

  • Pre- and post-processing in the context of a system refresh
    Doing this manually is a real challenge, error-prone, enormously time-consuming and the result will probably be incomplete.
    Forget all the strange descriptions with references to screenshots and manual configuration activities. With our product all the configuration data can be backed up before the system refresh and restored afterwards.
  • By mistake, all users of a client were locked out in the SAP system.
    This can happen in project go-lives or during maintenance tasks.There is no standard function available in an SAP system to help you out.
    • With this tool you can unlock users via database update. To do this, you need a user in another client on the same system. Use function "Unlock user via DB update" in category "Users".
  • Data in the system has to be corrected, but
    (1) there is neither a maintenance function nor a correction program available.
    or
    (2) the system / client settings does not allow to use the regular function (and there is no time or possibility to open the system / client resp. initiate this).
    Case 1 can happen for fields of tables without a table maintenance dialog - for example think of master data tables, status fields of Idocs which have been sent into your sytem twice by mistake or any other fields of tables that can not be maintained using the standard functions.
    Case 2 can happen for changing customizing data when the system / client is not open for customizing changes.
    • You can use this tool for deleting or updating table records via database update, possibly in combination with a selective "where" clause. Also a table maintenance function (can be used for inserting records) in a table editor is available.
      Use the functions in category "Table data".
    • If the data correction requires a more complex approach, you can also use the "Insert / modify a program" function to insert a correction program.    
  • You have to copy data from one system (or client) to another one

This might be useful for adjusting tables (e.g. customizing tables) between systems. Think, for example, of systems in different transport landscapes. There are 2 functions in the category "Table data" available for this purpose:

    • You can use the "Download / upload table data" function  for downloading data from one system / client (also a selection via a "where" clause is possible) and upload the data into another system / client. With this function you get the possibility to modify the data in front of the upload with a text editor. This function is suitable for small tables, and editing the data works best in case the fields in the table have a character representation (which, for example, is not the case for fields of type RAW).
    • You can use the "Process table data using R3trans" function. R3trans is a program from SAP and is used from the transport management system. It is a reliable tool also for big tables. In case you don't have to modify the data in front of the upload this is the recommended method.
  • You have to restore some tables in a system after a system copy
    Think of some data in a test system you want to have it available again in a test or project system. After a system copy by default all data is the same as on the system used as source for the copy (like regular updates of quality or test systems via copy from the productive system).
  • You want to make a backup of some important system-specific tables
    Think for instance of RFC connections, which are maintained specifically for every system. In case this data gets corrupted or lost there is no way to get them again from another system.  
    • Use the "Process table data using R3trans" function to store this data in a file which can be used using the same function to restore it in case it is necessary. Using the Command line tool you can also implement this function in an automation process, e.g. for a daily backup of system-specific data like RFC connections.
  • You have to lock specified users in front of a maintenance task and unlock them afterwards

There is of course the possibility to do this with the SU10 transaction, but it is cumbersome to select the users time and again, and there is no way to do this somehow automatically.

    • Use the "Lock user" and "Unlock user" functions to do this in a comfortable way. With the Command line tool you can also implement these functions in  an automation process.
  • You have to copy selected users from one system / client to another one (e.g. in a roll-in or carve-out)
    or
    You have to keep / restore user data on a system that will be overwritten via system copy.

There is no SAP standard function to do so. There is a client copy function and also a client export for users, but this includes all users in the source client and it overwrites all users in the target client. With this restriction in a roll-in project both functions are useless, in a carve-out it depends.

For keeping user data on a system that will be overwritten it might be usable in case you want to keep all users on the system. If not, it's useless, too.  

    • You can use the "Copy user" function in the category "Users" for specifying selected users to copy them from one system / client into another one. You also have the possibility to store the user data in a file on your computer and use this file later on to create the users in a system. Using the Command line tool you can also implement this function in an automation process, e.g. in an automation process of a system copy.
  • You have to set passwords for lots of users.

For example after a system copy you have to set the passwords to lots of system users to the previous individual values. There is no standard function available enabling you to do this in an easy way - every single user has to be maintained separately.

    • Use the "Set password" function in category "Users". You can either assign the same password or individual passwords to a set of users. Using the Command line tool you can also implement this function in an automation process, e.g. in an automation process of a system copy.
  • You need a specific information for each of your SAP systems.

One of your systems is being changed over - in which of your SAP systems do RFC connections to this system exist?

An employee is transferring to the competition - in which SAP systems is his user to be deleted?

Due to an antitrust case, you are required to analyze business data related to company xyz - which of your SAP systems should be considered for this?

Or do you just have another question that can be easily answered within a single SAP system - but which poses problems for you in a cross-system analysis in view of the large number of systems?

With "Shortcut for SAP systems" you can flexibly and quickly perform ad-hoc queries across systems.

For example lots of test users have to be created. You can create as much users as you want by specifying only the user ID's in a text field.

    • Use the "Create user"  function in category "Users". This function creates a user in the system with only few data. Once they are created you can use transaction SU10 to adjust company, defaults, parameters, role assignment etc. for all users or groups of users.
  • Your own (dialog) user does not have sufficient authorizations to do this or that.
    For example you have to get a glance on some data for which you are not authorized.
    • Lots of functions are available also for non dialog users. To pick up the example with the need for viewing data: use the function "View table data" in the category "Table data" with a non dialog user (which mostly have wider authorizations).
  • You urgently need to assign authorizations to a user, but your identity management system (for example One Identity Manager or SAP Identity Management) is currently down or the workflow is disrupted (for example due to absence of the approver).
    • Use the functions in the category "Authorizations" to be able assigning authorizations in emergency cases.
  • Your business is in danger and you have to insert an urgent correction program, but
    - the development system is down (for example an offline backup is running - usually at the weekend, when you are in the go-live activities :-(  )
    - the transport management system can not be used (no basis admin is available for doing the import)
    - the bureaucracy in the company is far to slow for enabling and allowing you to do the correction in time.